3.x: Fix parallel() on grouped flowable not replenishing properly #6719
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix a case when the
GroupedFlowable
is consumed by aparallel()
in fusion mode causing the source to stop replenishing items from the upstream, hanging the whole sequence.parallel()
was slightly different from the usual queue consumers because it checks forisEmpty
before trying topull
for an item. This was necessary because the rails may not be ready for more and an eagerpull
to check for emptyness would lose that item. The replenishing was done inGroupedFlowable.pull
but a call toGroupedFlowable.isEmpty
would not replenish.The fix is to have
isEmpty
replenish similar to whenpoll
detects emptyness and replenishes.Reported in reactor/reactor-core#1959